[Vertex AI] Update log message when API is not enabled #13733
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
paulb777
approved these changes
Sep 27, 2024
rachelsaunders
suggested changes
Sep 29, 2024
andrewheard
force-pushed
the
ah/vertexai-api-log
branch
from
cf8bea7 to
bddb11d
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
firebasevertexai.googleapis.comis not enabled to direct developers solely to the Firebase Console.InDEBUGbuilds, this situation is now afatalErrorinstead of an error log. This will quickly alert developers to the problem during development.To avoid crashing released apps, the message remains an error log in release builds.fatalErrorapproach breaks unit tests, always log at the error level.#no-changelog